Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use correct reporting path in app setup #1188

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Conversation

kneath
Copy link

@kneath kneath commented Dec 3, 2024

I noticed while setting this integration up that the customized server path (/data/report/?) must end with a /? in order for the integration to work correctly. The screenshot for ecowitt is correct, but the one for ambient weather and the supporting text was not. This updates the ambient weather image and documentation to use the correct reporting path.

Copy link

github-actions bot commented Jan 3, 2025

There hasn't been any activity on this pull request recently, so it has automatically been marked as stale and will be closed if no further action occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for some time label Jan 3, 2025
@bachya
Copy link
Owner

bachya commented Jan 3, 2025

Thanks for your patience/ I'm unclear on why this is necessary; I've not had to include a ? in the path for either my Ecowitt or Ambient Weather devices. Can you share in more detail what occurs on your end if this character is missing?

@kneath
Copy link
Author

kneath commented Jan 3, 2025

Hey @bachya — The question mark is required because the API endpoint for the docker container is /data/report/ — without the question mark, the reporting variables become a part of the path and it 404s. You can see the existing README has the ecowitt configuration containing the question mark:

image

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for some time label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants